The Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-254009	JUEX-RT-000370	SV-254009r844060_rule		High

Description
A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed. This requirement applies to both inbound and outbound network communications traffic. All inbound and outbound traffic must be denied by default. Firewalls and perimeter routers should only allow traffic through that is explicitly permitted. The initial defense for the internal network is to block any traffic at the perimeter that is attempting to make a connection to a host residing on the internal network. In addition, allowing unknown or undesirable outbound traffic by the firewall or router will establish a state that will permit the return of this undesirable traffic inbound.

Description

A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed. This requirement applies to both inbound and outbound network communications traffic. All inbound and outbound traffic must be denied by default. Firewalls and perimeter routers should only allow traffic through that is explicitly permitted. The initial defense for the internal network is to block any traffic at the perimeter that is attempting to make a connection to a host residing on the internal network. In addition, allowing unknown or undesirable outbound traffic by the firewall or router will establish a state that will permit the return of this undesirable traffic inbound.

STIG	Date
Juniper EX Series Switches Router Security Technical Implementation Guide	2023-03-23

Details

Check Text ( C-57461r844058_chk )
This requirement is not applicable for the DODIN Backbone. Review the router configuration to verify that the firewall filter is configured to allow specific ports and protocols and deny all other traffic. Associating any firewall filter to an interface will create a deny-all, permit-by-exception posture because each filter includes an implicit "deny all" final term. Verify firewall filters applied inbound on external interfaces are configured with terms permitting specific traffic. For example: [edit firewall] family inet { filter permitted_inbound_traffic_ipv4 { term 1 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv4; } protocol tcp; destination-port [ http https ]; } then accept; } term 2 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv4; } protocol udp; destination-port [ domain radius ]; } then accept; } } } family inet6 { filter permitted_inbound_traffic_ipv6 { term 1 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv6; } next-header tcp; destination-port [ http https ]; } then accept; } term 2 { from { destination-prefix-list { INSIDE_ADDRESSES_IPv6; } next-header udp; destination-port [ domain radius ]; } then accept; } } } Note: Although the example filter is sufficient to meet this requirement, an explicit "deny-all" term is required for logging. For example, add the following final term to both filters (IPv4 and IPv6) to enable logging of discarded packets: [edit firewall family (inet\|inet6) filter ] term default { then { log; syslog; discard; } } The filter must be configured inbound on all external interfaces. [edit interfaces] { unit { family inet { filter input permitted_inbound_traffic_ipv4; address ; } family inet6 { filter input permitted_inbound_traffic_ipv6; address ; } } Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example: input-list [ permit_mgt permit_routing_protocols default-deny ]; If the filter is not configured to allow specific ports and protocols and deny all other traffic, this is a finding. If the filter is not configured inbound on all external interfaces, this is a finding.

Check Text ( C-57461r844058_chk )

This requirement is not applicable for the DODIN Backbone.

Review the router configuration to verify that the firewall filter is configured to allow specific ports and protocols and deny all other traffic. Associating any firewall filter to an interface will create a deny-all, permit-by-exception posture because each filter includes an implicit "deny all" final term. Verify firewall filters applied inbound on external interfaces are configured with terms permitting specific traffic.

For example:
[edit firewall]
family inet {
filter permitted_inbound_traffic_ipv4 {
term 1 {
from {
destination-prefix-list {
INSIDE_ADDRESSES_IPv4;
}
protocol tcp;
destination-port [ http https ];
}
then accept;
}
term 2 {
from {
destination-prefix-list {
INSIDE_ADDRESSES_IPv4;
}
protocol udp;
destination-port [ domain radius ];
}
then accept;
}
}
}
family inet6 {
filter permitted_inbound_traffic_ipv6 {
term 1 {
from {
destination-prefix-list {
INSIDE_ADDRESSES_IPv6;
}
next-header tcp;
destination-port [ http https ];
}
then accept;
}
term 2 {
from {
destination-prefix-list {
INSIDE_ADDRESSES_IPv6;
}
next-header udp;
destination-port [ domain radius ];
}
then accept;
}
}
}

Note: Although the example filter is sufficient to meet this requirement, an explicit "deny-all" term is required for logging. For example, add the following final term to both filters (IPv4 and IPv6) to enable logging of discarded packets:
[edit firewall family (inet|inet6) filter ]
term default {
then {
log;
syslog;
discard;
}
}

The filter must be configured inbound on all external interfaces.
[edit interfaces]
{
unit {
family inet {
filter input permitted_inbound_traffic_ipv4;
address ;
}
family inet6 {
filter input permitted_inbound_traffic_ipv6;
address ;
}
}
Note: Some Juniper devices support both monolithic filters and filter lists. Filter lists separate each term, or set of terms, into a separate filter that is applied sequentially to an interface. If using filter lists, the keywords "input" or "output" change to "input-list" or "output-list". Verify the final list item is a deny-all filter. The deny-all filter is created once per family and can be reused across multiple lists. For example:

input-list [ permit_mgt permit_routing_protocols default-deny ];

If the filter is not configured to allow specific ports and protocols and deny all other traffic, this is a finding.

If the filter is not configured inbound on all external interfaces, this is a finding.

Fix Text (F-57412r844059_fix)
This requirement is not applicable for the DODIN Backbone. Configure the perimeter router to deny network traffic by default and allow network traffic by exception. For example: set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from protocol tcp set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port http set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port https set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 then accept set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from protocol udp set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port domain set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port radius set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 then accept set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from next-header tcp set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port http set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port https set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 then accept set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-prefix-list INSIDE_ADDRESSES set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from next-header udp set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port domain set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port radius set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 then accept Note: To enable logging, add the following as the final term to each filter: set firewall family [inet\|inet6] filter term default then log set firewall family [inet\|inet6] filter term default then syslog set firewall family [inet\|inet6] filter term default then discard set interfaces unit 0 family inet filter input permitted_inbound_traffic_ipv4 set interfaces unit 0 family inet address set interfaces unit 0 family inet6 filter input permitted_inbound_traffic_ipv6 set interfaces unit 0 family inet6 address

Fix Text (F-57412r844059_fix)

This requirement is not applicable for the DODIN Backbone.

Configure the perimeter router to deny network traffic by default and allow network traffic by exception. For example:

set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from protocol tcp
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port http
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 from destination-port https
set firewall family inet filter permitted_inbound_traffic_ipv4 term 1 then accept
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from protocol udp
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port domain
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 from destination-port radius
set firewall family inet filter permitted_inbound_traffic_ipv4 term 2 then accept

set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from next-header tcp
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port http
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 from destination-port https
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 1 then accept
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-prefix-list INSIDE_ADDRESSES
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from next-header udp
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port domain
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 from destination-port radius
set firewall family inet6 filter permitted_inbound_traffic_ipv6 term 2 then accept

Note: To enable logging, add the following as the final term to each filter:
set firewall family [inet|inet6] filter term default then log
set firewall family [inet|inet6] filter term default then syslog
set firewall family [inet|inet6] filter term default then discard

set interfaces unit 0 family inet filter input permitted_inbound_traffic_ipv4
set interfaces unit 0 family inet address
set interfaces unit 0 family inet6 filter input permitted_inbound_traffic_ipv6
set interfaces unit 0 family inet6 address